Skip to content

💥 Record task latency even for WFT failures that were dropped#1207

Merged
Sushisource merged 2 commits intomasterfrom
normalize-metric
Apr 9, 2026
Merged

💥 Record task latency even for WFT failures that were dropped#1207
Sushisource merged 2 commits intomasterfrom
normalize-metric

Conversation

@Sushisource
Copy link
Copy Markdown
Member

What was changed

See title. This brings Core's reporting on this metric in-line with Go and Java. This is technically a breaking change as the metric is now recorded in more situations than it was previously, but we've decided that's worth it given the minor nature of the change and the benefit of consistency.

Why?

Consistency

Checklist

  1. Closes [Bug] Worker Heartbeat: wf_task_latency doesn't always match 1:1 with total_processed_tasks #1202

  2. How was this tested:
    Added UT

  3. Any docs updates needed?

@Sushisource Sushisource requested a review from a team as a code owner April 8, 2026 21:53
Comment on lines +1734 to +1737
let body = get_text(format!("http://{addr}/metrics")).await;
let latency_line = body
.lines()
.find(|l| l.starts_with("temporal_workflow_task_execution_latency_count{"));
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe wrap in an eventually in case it takes a bit for metrics to populate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Worker Heartbeat: wf_task_latency doesn't always match 1:1 with total_processed_tasks

2 participants